home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Eagles Nest BBS 7
/
Eagles_Nest_Mac_Collection_Disc_7.TOAST
/
>>UPLOAD FRESH WARES<<
/
AudioDeck206
/
Audiodeck 2.0.6 ƒ
/
Driver Limitations
< prev
next >
Wrap
Text File
|
1994-08-19
|
3KB
|
73 lines
Here's the tests I made on my Quadra 660AV to know who much compatible is the
third-party drivers are to Apple's 5.x drivers. All this anomalies are
*NOT* caused by Audiodeck (or not as far as I know). Audiodeck follows
the standard suite of calls, and don't do anything fancy (well, it
depends what you call fancy or not).
FWB (with AppleCD300i drive)
----------------------------
Most of these problems are reproductible with CDT Remote program, which
comes with FWB's drivers.
- When switching modes, or selecting a new track, you might hear some
glitches with the sound (the sound going down and back up very fast).
This is the reaction of CD-ROM Toolkit when asked to stop at a certain
track (it's a bug if you ask me). To solve this problem, I lower
the CD-ROM volume to 0, then, I raise it back after the play command
is issued. This in fact remove the glitch when asking to play.
- On *SOME* discs (I've tried 10 discs, and about 3-4 showed this behaviour),
when on stop and ask Audiodeck to play the first track, by either
double clicking on the playlist, pressing play, or selecting
the first track via the popup menu, Audiodeck will start playing
the track, and then skip to the next. Why?! For some reason, FWB's
change the current status from Play to Stop, fooling Audiodeck. This
is all true ONLY when the first track is the track #1 ;-). Also,
it is possible that a disc that showed this behaviour on a particular
session won't show it on a next reboot...
- FWB doesn't support the command to stop at a particular track.
Or I just can't make it to do it. This result in the fact that
if your computer is pretty busy, Audiodeck might not have the
time to notice that it is currently playing a de-activated track
or a track which is not suppose to be played.
For exemple, let say that the playlist order is 4,3,2,6,5,1; Audiodeck
is currently playing track 2; your computer is too busy and Audiodeck
can't notice that the track 2 is finished; track *3* starts to
play, but as soon Audiodeck get some CPU time back, it will
skip to track 6. With Apple's drivers, the CD will STOP after
2 because Audiodeck asked to drivers to STOP after 2.
- The volume react like Apple CD-ROM 4.x. I mean when you drag the
volume slider around the 1/3 of the slider, the sound volume will
be near/at zero.
- When using the backward scanning button, sometimes FWB driver will
switch itself to Stop mode, once again fooling Audiodeck into
believe the track has ended, and Audiodeck will issue a Play
command for the next track.
Spirit
------
- Quite simple, Spirit CD 1.40 doesn't work on my Macintosh with my
Apple CD300 drive. Sorry, no comments about this driver. But
as far as I heard, Audiodeck is pretty useless with it since
Spirit drivers doesn't seems to report the correct Current Track
confusing Audiodeck into thinking that the track ended and should
skip to the next one. Well, to be sure, just try Audiodeck with
your system and see for yourself.
Apple 4.x
---------
- When you drag the volume slider around the 1/3 of the slider, the
sound volume will be near/at zero. This is a bug in the driver.
Apple 5.x
---------
- Works like a charm :-).